docs(scim): added entra id support for scim#6438
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
|
@ohlookadollar - Had to add an exception to Headings.yml so CI doesn't trip on sentence casing for Entra ID |
…he **Secret Token** section
…into chore/add-more-supported-mysql-types
| <PrivatePreviewBadge/> | ||
|
|
||
| :::note | ||
| SCIM provisioning is in private preview. |
There was a problem hiding this comment.
Use of the PrivatePreviewBadge makes this note redundant, I would remove this.
|
|
||
| Tokens can't be recovered. In **Organization settings → SAML and SCIM settings → SCIM Configuration** in the ClickHouse Cloud Console, revoke the lost token and generate a new one, then update the **Secret Token** in Entra ID. | ||
|
|
||
| ## Frequently asked questions {#faq} |
There was a problem hiding this comment.
I know that the structure of the pre-existing guide was followed, but I find it odd that this faq section and the troubleshooting section are formatted differently. Non-blocking, but perhaps we should make this consistent.
If we want to go above and beyond, which does not have to be in the scope of this pr, we could do an faq section similar to https://clickhouse.com/docs/use-cases/observability/clickstack/faq
Happy to help with this, and it goes beyond the scope of this pr's content, so I'd open a follow up for some formatting fix ups.
There was a problem hiding this comment.
@dhtclk changed it have the same format as the clickstack faq, is this sufficient or you prefer it be in its own standalone page?
There was a problem hiding this comment.
I think that's great! Thank you!
…ent with clickstack
|
@ohlookadollar - I'll pull main again to fix the CI, once I can verify the preview build and do another once over I'll approve and merge if you're ready! |
@dhtclk Thank you!, please merge when its ready 🙏 |
2 participants
Summary
Adds a new guide, SCIM provisioning with Microsoft Entra ID, mirroring the
existing Okta SCIM guide and adapted to Entra's provisioning model (automatic
provisioning, bearer-token auth via the Secret Token field formatted as
<scim-key>:<scim-secret>, attribute mappings, assigned-scope provisioning, andthe ~40-minute sync cycle / Provision on demand).
Also updates the Okta guide (
07b_scim-setup.md) — its intro and FAQ previouslystated Entra ID was unsupported because auth was "Basic Auth only"; corrected to
note the endpoint accepts both Basic Auth (Okta) and a bearer token (Entra ID),
with a cross-link to the new guide. Adds the new page to the Cloud access
management index.
No existing URLs change (the new page is a new slug,
/cloud/security/scim-setup-entra).Checklist